-
-
Notifications
You must be signed in to change notification settings - Fork 35
feat: Ref/Value behavior tracking #1755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
pkg.pr.new packages benchmark commit |
reference to something define in that function)
the value proxies
|
Something weird happened to the vaporrave example, some of the effects seem to have disappeared. Also, Slime Mold 3D throws when switching to another example, but this might have been the case before. |
aleksanderkatan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job!
Some of my old comments got lost in the "hidden items".
apps/typegpu-docs/src/content/docs/reference/shader-generation.mdx
Outdated
Show resolved
Hide resolved
| computeLayout.$.inState[currentId].mass < | ||
| computeLayout.$.inState[otherId].mass | ||
| ) { | ||
| const current = computeLayout.$.inState[currentId]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still is weird to me that this translates to a pointer. It makes sense in JS though. This may just be me coming from C, t[i] being equivalent to *(t+i).
aleksanderkatan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's goooo!
Changes:
conststatements be pointers if they take in a referential type (let statements)conststatements with naturally non-referential types to be WGSLconst🎉TODO:
const some = layout.$.data) local to functions, and not leak into shell-less functions signatures. This ensures that a function doesn't accidentally have access to a value it shouldn't have access to.Reference assignment errors:
Invalid 'let' statement errors:
